se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Fall |
Prerequisites | None | |||||
Course Language | ||||||
Course Type | Required | |||||
Course Level | - | |||||
Mode of Delivery | - | |||||
Teaching Methods and Techniques of the Course | ||||||
Course Coordinator | ||||||
Course Lecturer(s) | ||||||
Assistant(s) | - |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | X |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Introduction | SWEBOK |
2 | Engineering, software engineering | Sommerville, Software Engineering, 9e, Pearson, 2011. (ch.1). |
3 | Software processes | Sommerville, (ch.2) |
4 | Agile software development | Sommerville, (ch.3) |
5 | Requirements engineering | Sommerville, (ch.4) |
6 | System modeling | Sommerville, (ch.5) |
7 | System modelling | Sommerville, (ch.5) |
8 | Midterm exam | |
9 | Architectural design | Sommerville, (ch.6) |
10 | Design and implemantation | Sommerville, (ch.7) |
11 | Design and implementation | Sommerville, (ch.7) |
12 | Software testing | Sommerville, (ch.8) |
13 | Software evolution | Sommerville, (ch.9) |
14 | Software maintenance | Sommerville, (ch.9) |
15 | Review | |
16 | Review of the Semester |
Course Notes/Textbooks | Sommerville, Software Engineering, 9e, Pearson, 2011. |
Suggested Readings/Materials | * Pressman, Software Engineering: A Practitioner's Approach, 7e, McGrawHill, 2010. * SWEBOK, Guide to the Software Engineering Body of Knowledge: 2004, IEEE. * Fowler, UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3/e, AddisonWesley, 2004. * Larman, Applying UML and Patterns: An Introduction to ObjectOriented Analysis and Design and Iterative Development, 3/e, Pearson, 2005. * C. Sidney Burrus, What is Engineering?, http://cnx.org/content/m13680/latest/Understanding the Engineering Problem Solving Process, http://www.asme.org/ Education /PreCollege/TeacherResources/StudentReading22.cfm * Richard H.Thayer, Software System Engineering: A Tutorial, April 2002. * F.P. Brooks, Jr , No Silver Bullet: Essence and Accidents of Software Engineering, Proceedings of the IFIP Tenth World Computing Conference: 10691076, 1986. * European Software Strategy, www.nessieurope.eu, June 2008. |
Semester Activities | Number | Weigthing |
Participation | - | - |
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques | ||
Portfolio | ||
Homework / Assignments | ||
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 40 |
Final Exam | 1 | 60 |
Total |
Weighting of Semester Activities on the Final Grade | 1 | 40 |
Weighting of End-of-Semester Activities on the Final Grade | 1 | 60 |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 2 | 32 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
Study Hours Out of Class | 16 | 5 | |
Field Work | |||
Quizzes / Studio Critiques | |||
Portfolio | |||
Homework / Assignments | |||
Presentation / Jury | |||
Project | |||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | ||
Final Exams | 1 | ||
Total | 112 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | X | ||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | X | ||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | X | ||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | X | ||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | X | ||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | X | ||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | X | ||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest